home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
wildcat
/
wcff351.zip
/
WCFF.DOC
< prev
next >
Wrap
Text File
|
1992-09-26
|
53KB
|
1,278 lines
WILDCAT! FILE FORWARD
WCFF! v3.51
(C) Copyright 1989, 1992 by Online Computer Resources
All Rights Reserved
Revised: 09/26/92
WCFF!
TABLE OF CONTENTS
ACKNOWLEDGEMENTS . . . . . . . . . . . . . . . . . . . . . 1
FILES INCLUDED . . . . . . . . . . . . . . . . . . . . 1
PRODUCT EVALUATION . . . . . . . . . . . . . . . . . . . . 2
NEW KEY FILE . . . . . . . . . . . . . . . . . . . . . 2
REGISTRATION/ORDERING INFORMATION . . . . . . . . . . 2
PRODUCT ENHANCEMENT . . . . . . . . . . . . . . . . . . . . 3
FEATURES . . . . . . . . . . . . . . . . . . . . . . . 3
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . 4
PROGRAM DESCRIPTION . . . . . . . . . . . . . . . . . 4
HOW DOES WCFF! WORK? . . . . . . . . . . . . . . . . . 4
UPGRADE/INSTALLATION . . . . . . . . . . . . . . . . . . . 5
UPGRADING WCFF! FROM PREVIOUS VERSIONS . . . . . . . . 5
INSTALLING WCFF! FOR THE FIRST TIME . . . . . . . . . 5
COMMAND LINE OPTIONS . . . . . . . . . . . . . . . . . . . 6
COMMAND LINE USAGE . . . . . . . . . . . . . . . . . . 6
-N . . . . . . . . . . . . . . . . . . . . . . . 6
-T . . . . . . . . . . . . . . . . . . . . . . . 6
-? or ? or /? . . . . . . . . . . . . . . . . . . 6
HATCHING FILES . . . . . . . . . . . . . . . . . . . . 6
FULL SCREEN HATCHING MODE . . . . . . . . . . . . . . 7
FILENAME TO HATCH . . . . . . . . . . . . . . . . 7
WILDCAT! FILE AREA . . . . . . . . . . . . . . . 7
DESCRIPTION . . . . . . . . . . . . . . . . . . . 7
AREA NAME . . . . . . . . . . . . . . . . . . . . 7
COMMAND LINE HATCHING MODE . . . . . . . . . . . . . . 8
-A[area name] . . . . . . . . . . . . . . . . . . 8
-F[file name] . . . . . . . . . . . . . . . . . . 8
-D[description file] . . . . . . . . . . . . . . 8
WCFF.CFG CONFIGURATION . . . . . . . . . . . . . . . . . . 9
WCFF.CFG DESCRIPTION . . . . . . . . . . . . . . . . . 9
ORIGZONE . . . . . . . . . . . . . . . . . . . . 9
NETNODE . . . . . . . . . . . . . . . . . . . . . 9
AKA . . . . . . . . . . . . . . . . . . . . . . . 9
WILDCAT . . . . . . . . . . . . . . . . . . . . . 9
INFILES . . . . . . . . . . . . . . . . . . . . . 10
INMAIL . . . . . . . . . . . . . . . . . . . . . 10
OUTFILES . . . . . . . . . . . . . . . . . . . . 10
OLDFILES . . . . . . . . . . . . . . . . . . . . 10
i
WCFF!
TABLE OF CONTENTS
MAILER TYPE CONFIGURATION . . . . . . . . . . . . 11
FIDO . . . . . . . . . . . . . . . . . . . . . . 11
MAIL . . . . . . . . . . . . . . . . . . . . . . 11
BINKLEY . . . . . . . . . . . . . . . . . . . . . 11
OUTBOUND . . . . . . . . . . . . . . . . . . . . 11
CRC . . . . . . . . . . . . . . . . . . . . . . . 12
POSTTOFROM . . . . . . . . . . . . . . . . . . . 12
POSTTOSUBJECT . . . . . . . . . . . . . . . . . . 12
POSTTONOTE . . . . . . . . . . . . . . . . . . . 12
POSTTOORIGIN . . . . . . . . . . . . . . . . . . 12
AREA . . . . . . . . . . . . . . . . . . . . . . 13
COMMAND LINE PARAMETERS . . . . . . . . . . 13
<drive:directory> . . . . . . . . . . . 13
<area name> . . . . . . . . . . . . . . 13
<area # or P> . . . . . . . . . . . . . 13
LOCAL POSTTOAREA . . . . . . . . . . . . . . 14
LOCAL POSTTOFROM . . . . . . . . . . . . . . 14
LOCAL POSTTOSUBJECT . . . . . . . . . . . . 14
LOCAL POSTTONOTE . . . . . . . . . . . . . . 14
LOCAL POSTOORIGIN . . . . . . . . . . . . . 15
LOCAL CRC . . . . . . . . . . . . . . . . . 15
<zone:net/node> . . . . . . . . . . . . . . 15
<password> . . . . . . . . . . . . . . . . . 15
<flags> . . . . . . . . . . . . . . . . . . 16
NEWFILESLIST . . . . . . . . . . . . . . . . . . 17
ADDITIONAL INFORMATION . . . . . . . . . . . . . . . . . . 18
REVISION HISTORY . . . . . . . . . . . . . . . . . . . 18
ERRORLEVELS . . . . . . . . . . . . . . . . . . . . . 18
TECHNICAL SUPPORT . . . . . . . . . . . . . . . . . . . . . 19
WCFF! LICENSING AND DISTRIBUTION AGREEMENT . . . . . . . . 20
NO WARRANTY . . . . . . . . . . . . . . . . . . . . . 21
APPENDIX A . . . . . . . . . . . . . . . . . . . . . . . . 22
MEMORY REQUIREMENTS . . . . . . . . . . . . . . . . . 22
REQUIREMENTS/LIMITATIONS OF WCFF! . . . . . . . . . . 22
ii
WCFF! v3.51 Page 1
ACKNOWLEDGEMENTS
ACKNOWLEDGEMENTS
Thanks go to Mustang Software Inc. for creating an exceptional
product in WILDCAT! v3.x. Without their product, there would be no
use for WCFF!.
Many thanks go to the BETA testers of WCFF!. Without their patience
and understanding along with all the suggestions for features, WCFF!
would not have become what it is today.
FILES INCLUDED
WCFF! is distributed in a single compressed library file containing
these files:
READ.ME Introductory comments and any last minute
changes.
WHATSNEW.351 Enhancements/bug fixes in this version
REGISTER.DOC Registration form used when registering the
product.
WCFF.EXE WCFF!, the executable.
WCFF.DOC This documentation file.
WCFF.CFG Sample configuration file for WCFF!.
WCFF! v3.51 Page 2
PRODUCT EVALUATION
NEW KEY FILE
With this new release of WCFF! comes an updated method of allowing
the 30 day evaluation period. Key files may be obtained by logging
on to the support board and selecting the "Key Generation" option
from the Main Menu. After the selection is made, you simply enter
in the required information and follow the instructions for
downloading.
Only one key per person/registration number will be allowed. The
WCFF! support board may reached by dialing:
Node-1 (510) 687-0236 - USR D/S
Node-2 (510) 687-2134 - V32bis
This version of WCFF! is fully featured with all the options enabled
for the duration of the evaluation period. If you haven't
registered the product after the thirty day evaluation period, WCFF!
will inform you it has expired and will simply cease to run. File
Requests (FREQ) for key files are not allowed.
REGISTRATION/ORDERING INFORMATION
WCFF! carries a $25 plus $2 shipping and handling registration fee.
VISA, MasterCard and Discover cards are welcome. To place an order,
you may call us directly at (510) 687-1122 and use your credit card
or simply mail in the REGISTER.DOC file along with your check.
When placing an order using a credit card, key files can generally
be made available for download the very same day. A diskette
containing your key file and the most current copy of WCFF! is
usually shipped the following day.
If payment is made via check, there will be a 10 day hold placed on
the order allowing time for the check to clear the bank prior to
shipment. At the end of the 10 day period, the key file can be put
up for download (if so requested) and the diskette will then be
mailed out. See the enclosed REGISTER.DOC file for specific
registration information.
International (except Australia) and USA orders are handled by us
at Online Computer Resources. Australian orders are handled by
Barcastle Enterprises located in Melbourne, Australia. Please see
the enclosed REGISTER.DOC file for additional ordering information.
WCFF! v3.51 Page 3
PRODUCT ENHANCEMENT
FEATURES
o Replace feature allows files to be updated if the
incoming file has a later date/time. The old file is
copied to a directory of your choice for storage.
o WCFF! is totally RAID compatible.
o Full screen HATCH feature. You can hatch a file into
WILDCAT!, out of WILDCAT! or as a PASSTHRU.
o Command line HATCH. WCFF! can hatch files in
unattended mode.
o Number of areas/nodes that WCFF! can process is only
limited by the amount of memory you have available.
o If RAID is used to auto-create areas, WCFF! will send a
netmail message notifying you that there is an auto-
created area line that needs your attention.
o TICs are renamed to .BFF instead of .BAD if they are
unable to be processed.
o Enhanced logging of files being processed in the log
file.
o WCFF! will create echomail messages for areas if told to
do so, specifying the name, description, file size etc.
of the incoming file.
o PASSTHRU support. Areas can be defined as PASSTHRU
which means that the incoming file is not added to the
WILDCAT! database.
o CRC checking can be turned on/off for individual areas.
o Added AKA support where you can specify which AKA to
use when sending files to a node.
o Help option is available from the command line.
o Added an option so that nodes do not have to receive a
.TIC file with the file that was sent to them.
o Support for file scanners such as CATSCAN for automatic
virus scanning and so on.
WCFF! v3.51 Page 4
INTRODUCTION
PROGRAM DESCRIPTION
WCFF! v3.51 is a Fidonet compatible utility program to import files
and their one-line descriptions into your WILDCAT! v3.xx system, and
to export/forward files on to other systems. This is based on a
distribution scheme much like Fidonet compatible echomail is
imported/exported from the WILDCAT! message conferences. WCFF! is
the equivalent of FLEA and TICK, except that it is specific to
WILDCAT! and thus will not operate on any other type of BBS system.
WCFF! is totally compatible with both FLEA and TICK, and as such can
read in FLE and TIC files properly.
Files exported can be put in either TIC or FLE format and will
adhere to the specifications as defined by Barry Geller (author of
TICK) or Ron Bemis (author of FLE). WCFF! is fully multi-line
compatible allowing callers to be using the BBS while WCFF! is
processing files. However, multiple copies of WCFF! running
simultaneously is NOT supported.
HOW DOES WCFF! WORK?
After checking for the presence of WCFF.CFG, WCFF! reads the
contents and stores this information in memory. This file is used
to tell WCFF! where to find certain areas or files on your system,
and also specifies all the different file areas you will be
receiving and/or forwarding from your system. WCFF! then reads the
WILDCAT! configuration files and gets the location of the necessary
data files and then prepares them for processing.
WCFF! then searches the INFILES directory path looking for any FLE
and TIC files. Each FLE/TIC file found is read and the associated
file is then added to the WILDCAT! file database and if necessary,
forwarded on to any other nodes as specified. If the file already
exists in WILDCAT! database, the older dated file will be
transferred to the OLDFILES directory and the new one will replace
it. After adding the TIC/FLE information into the respective file
area, the actual file is then transferred to the respective sub-
directory and made available for download (if so allowed in
MAKEWILD).
This process is repeated until such time as all incoming FLE or TIC
files have been processed. All activity is logged in detail in the
WCFF.LOG file so that if any problems are encountered, any pertinent
information will be found there.
WCFF! v3.51 Page 5
UPGRADE/INSTALLATION
UPGRADING WCFF! FROM v3.50
Since this version is primarily a bug fix, the upgrade procedure is
very simple.
1) Using PKUNZIP, uncompress the contents of WCFF351.ZIP
into a temporary subdirectory.
2) In the directory where the old WCFF.EXE is located,
replace it with the new WCFF.EXE file (located in the
temporary subdirectory).
3) Optionally, edit your existing WCFF.CFG file and add the
NEWFILESLIST command. Refer to the section on this
command for additional configuration information.
UPGRADING WCFF! FROM EARLIER VERSIONS
Since there are too many changes to the configuration file to
warrant a specific step by step upgrade procedure, we strongly
suggest you use the example WCFF.CFG file and modify it to your
exact needs.
INSTALLING WCFF! FOR THE FIRST TIME
Below is a list of step by step instructions for installing WCFF!
on your system.
1) Create a sub-directory called \WCFF.
2) Copy the distribution archive, WCFF351.ZIP into the newly
created \WCFF sub-directory and then uncompress it.
3) Using a standard ASCII text editor, edit the WCFF.CFG
file so that it conforms to path and configuration
requirements of your system. Please refer to the
appropriate section on the WCFF.CFG file for details on
configuration information.
WCFF! v3.51 Page 6
COMMAND LINE OPTIONS
COMMAND LINE USAGE
WCFF! <-N> <-T> <HATCH> <-?> <?> </?> <-A[area name]>
<-F[file name]> <-D[description file]>
Example Usage: WCFF! -T
Below is a description of each of the command line options available
when executing WCFF!
-N Disables the auto-cleanup mode that WCFF! does after each
run. Auto-cleanup deletes orphaned .TIC files. This
works in FIDO mode only!
-T Enables the truncate (delete) mode in a Binkley
environment. Please use with caution!
-? or ? or /?
Displays a screen containing help information on the
available command line options.
HATCHING FILES
WCFF! has the ability to "hatch" or prepare a file(s) to be
transmitted by creating the necessary TIC/FLE file and associated
netmail message or FLO/CLO/HLO files (depending on mailer type) for
transmission on to other systems. This can be accomplished in
either of two methods, full screen or command line mode.
Full screen mode has the ability to process file(s) from the WC30
database allowing immediate hatching of files for distribution.
Command line mode offers you the ability to automate forwarding of
files at specific times by invoking WCFF! from a batch file with the
necessary command line parameters. Each method of hatching files
offers you the necessary flexibility for fast and efficient file
distribution.
WCFF! v3.51 Page 7
COMMAND LINE OPTIONS
FULL SCREEN HATCHING MODE
Full screen mode allows you to perform an immediate hatch of a file
for distribution. WCFF! first checks to see if the file exists in
the WC30 database and then obtains the one line description from the
database allowing you to make any changes prior to actually hatching
the file.
To invoke full screen hatch mode, change to the \WCFF directory and
at the DOS prompt type:
WCFF HATCH
Shown below is a sample screen.
╔══════════════ WILDCAT! File Forward Hatch v3.51 ═════════════════╗
║ ║
║ Filename to hatch: WILDCAT! File Area: ║
║ ║
║ Description : ║
║ ║
║ Area Name : ║
║ ║
╚ ESC -> EXIT (do not hatch) ════════════ F10 -> SAVE (hatch file) ╝
Filename to hatch:
This is the actual file name as it exists in the WC30 database
that you wish to hatch.
WILDCAT! File Area:
This is the file area as defined in MAKEWILD that the above
file name is located in.
Description:
This is the one line description as entered in the WC30 files
database. You have the ability to modifiy this to your
requirements prior to saving.
Area Name:
This is the associated file area name you wish this file to be
distributed under. Up to 15 characters are allowed and it's
used similarly to the message conference names in your
AREAS.BBS file for echomail.
Once the above information is properly defined, pressing [F10] will
save this information and create the necessary TIC/FLE file and
netmail message (or FLO/HLO/CLO file) for transmission on to the
addresses defined in the WCFF.CFG file. Likewise, pressing the
[ESC] key will abort the hatching process and return you to the DOS
prompt.
WCFF! v3.51 Page 8
COMMAND LINE OPTIONS
FULL SCREEN HATCHING MODE - (continued)
NOTE: For the full screen hatch mode to work properly, you MUST
put your OWN ADDRESS as a <zone:net/node number> in the
file AREA you will be hatching into with a password of
HATCH. THIS IS VERY IMPORTANT!!
COMMAND LINE HATCHING MODE
The command line mode allows you to hatch files by defining the
necessary file information via command line parameters. Since
hatching is being performed from the command line, all three (3)
command line parameters (-A, -F and -D) MUST BE SPECIFIED before
WCFF! will hatch the file. Shown below is a COMPLETE sample command
line used to hatch a file.
WCFF -Asoftdist -Ftest.zip -Dc:\desc\test.txt
-A[area name]
This is used to define the actual file area name this
file should be distributed under. This is similar to the
message conference name in your AREAS.BBS file for
echomail. This is the same name as was previously
defined via the AREA name in your WCFF.CFG file. A
maximum of 15 characters are allowed.
Example Usage: WCFF -Asoftdist
-F[file name]
This is the name of the file you wish to hatch. It MUST
exist in your INFILES directory. You do not need the
full path, just the file name.
Example Usage: WCFF -Ftest.zip
-D[description file]
This is the name of the file that contains the
description for the file you want to hatch. This file
contains only one (1) line and the description should be
no longer than 60 characters.
Example Usage: WCFF -Dc:\desc\test.txt
or
WCFF -Dtest.txt
WCFF! v3.51 Page 9
WCFF.CFG CONFIGURATION
WCFF.CFG DESCRIPTION
The WCFF.CFG file is a standard ASCII text file used to control
the operating characteristics of WCFF! during normal operation.
This file is REQUIRED for proper operation.
Any standard ASCII text editor can be used when making changes.
Comments can be contained in this file for easy reference by
placing a semicolon ";" in the first position of any line.
Spaces are ignored and BLANK lines are only allowed between
file AREA definitions.
Shown below is a list of commands used for the configuration
process.
ORIGZONE <zone number> [REQUIRED]
This is your zone number. WCFF! is zone aware so do NOT leave
this out.
Example Usage: ORIGZONE 1
NETNODE <net/node> [REQUIRED]
This is the address of your system.
Example Usage: NETNODE 161/503
AKA <zone:net/node> [OPTIONAL]
This is your alias address. If you have more than one alias,
then you should create a new AKA line for each address your
know as. ZONE is required! Maximum of 15 AKA's are allowed.
Example Usage: AKA 1:161/999
Sequential placement (top to bottom) in the WCFF.CFG file
constitutes the numbering sequence used in the AREA command's
<An> flag.
WILDCAT <drive:\directory> [REQUIRED]
This is the location of your WILDCAT! configuration files.
This is often referred to as the WILDCAT! HOME directory.
Example Usage: WILDCAT c:\wc30
WCFF! v3.51 Page 10
WCFF.CFG CONFIGURATION
INFILES <drive:\directory> [REQUIRED]
This is the directory name where all your inbound files reside.
WCFF! will look in this directory for new TIC/FLE files to be
processed.
Example Usage: INFILES c:\fd\file
INMAIL <drive:\directory> [REQUIRED]
This is the directory name where your mailer stores any inbound
mail archives/PKT files. WCFF! creates .PKT files via the
LOCAL POSTTOAREA option and will use this path to store them
for later processing INTO the WC30 message base via a mail
tosser such as WILDMAIL!
Since D'Bridge has separate directories for inbound files and
inbound mail archives, this option is used to define the
location of mail archives/PKT files only!. For FrontDoor
systems, this is normally the same as the path defined for
INFILES.
Example Usage: INMAIL c:\db\mail
OUTFILES <drive:\directory> [REQUIRED]
This is the sub-directory where you want your OUTBOUND TIC/FLE
files to be stored. This can be a unique subdirectory to keep
your TIC/FLE files separate from other files. This will make
for better organization on your system.
Example Usage: OUTFILES c:\fd\ticfiles
OLDFILES <drive:\directory> [REQUIRED]
This is the location where you want all the old files to reside
that WCFF! has overwritten. When inbound file(s) have the same
name as those already in the database, but with a newer file
date, WCFF! will place the older file here for examination
instead of simply overwriting the older file with the newer
one. This allows for review prior to deletion.
Example Usage: OLDFILES c:\oldfiles
WCFF! v3.51 Page 11
WCFF.CFG CONFIGURATION
MAILER TYPE CONFIGURATION
WCFF! needs to know what mailer type you will be using to properly
establish the type of files, locations and formats to use. When you
select the mailer type, you will also be selecting the appropriate
WCFF! commands unique to that mailer. In other words, selecting
FIDO, you also need to select MAIL. BINKLEY and OUTBOUND commands
must be COMMENTED OUT by placing a semicolon ; in front of them.
Likewise, selecting BINKLEY requires the OUTBOUND command. FIDO and
MAIL must then MUST BE COMMENTED OUT! You must NOT mix mailer
specific commands otherwise WCFF! will NOT run.
FIDO [REQUIRED if using FD/DB]
This tells WCFF! to operate in Fido specific mode. If you
select this mode, then the MAIL option MUST be specified
showing the location of your netmail directory and BINKLEY and
OUTBOUND commands MUST BE COMMENTED OUT. If you're running
D'Bridge or Frontdoor, you must use this option.
Example Usage: FIDO
MAIL <drive:\directory> [REQUIRED for FIDO ONLY]
This is the location of the netmail directory for WCFF! to
place it's outbound netmail messages. This option MUST be used
if the FIDO mode is selected.
Example Usage: MAIL c:\fd\netmail
BINKLEY [REQUIRED if using Binkley]
This tells WCFF! to operate in Binkley mode, and thus will
create FLO files in the directory specified in the OUTBOUND
option. The OUTBOUND option MUST be specified! When using
this option, FIDO and MAIL options MUST NOT BE SELECTED!
Example Usage: BINKLEY
OUTBOUND <drive:\directory> [REQUIRED for BINKLEY ONLY]
This is the location of the outbound directory. This is where
WCFF! will place the outbound FLO/HLO/CLO files. This option
must be used if BINKLEY mode has been selected. When using
this option, FIDO and MAIL options MUST NOT BE USED!
Example Usage: OUTBOUND c:\binkley\outbound
WCFF! v3.51 Page 12
WCFF.CFG CONFIGURATION
CRC [OPTIONAL]
This option is used to check the CRC-32 value in the .TIC file
against the actual CRC value of the file received. If there
is a match, this indicates the file is original (according to
the .TIC) and is then considered a valid/original file. If for
some reason the two CRC values do not match, the file is then
renamed to .BAD.
If this option is not used, then the CRC is not checked, but
all outgoing .TIC files created by WCFF! will have the correct
calculated CRC value in them.
Example Usage: CRC
POSTTOFROM <user name> [OPTIONAL]
This option allows you to specify the FROM: field of the
echomail message that gets created if you use the LOCAL
POSTTOAREA option. Maximum of 36 characters.
Example Usage: POSTTOFROM Derek Koopowitz
POSTTOSUBJECT <text for subject line> [OPTIONAL]
This option allows you to specify the content of the SUBJECT:
line of the echomail message that gets created if you use the
LOCAL POSTTOAREA option. Maximum of 72 characters.
Example Usage: POSTTOSUBJECT New Files Received
POSTTONOTE <note text> [OPTIONAL]
This option allows you to specify the content of the note field
placed in the message body of the echomail message that gets
created. Maximum of 72 characters.
Example Usage: POSTTONOTE Files available for downloading
POSTTOORIGIN <origin line> [OPTIONAL]
This option allows you to specify the origin line you would
like appended to each echomail message that gets created.
Maximum of 66 characters and MUST include your zone:net/node
address enclosed in parenthesis.
Example Usage: POSTTOORIGIN The Power Station (1:161/123)
WCFF! v3.51 Page 13
WCFF.CFG CONFIGURATION
AREA <drive:\directory> <area name> <file area # or P> [REQUIRED]
LOCAL POSTTOAREA <local echo name>
LOCAL POSTTOFROM <user name>
LOCAL POSTTOSUBJECT <text for subject line>
LOCAL POSTTONOTE <note text>
LOCAL POSTTOORIGIN <origin line>
LOCAL CRC <ON|OFF>
<zone:net/node> <password> <flag(s)>
. . .
. . .
<zone:net/node> <password> <flag(s)>
The AREA command is used to define a specific file area for
importing or exporting, automatic message generation (if used) and
the participating node addresses. The number of AREA statements
allowed is only limited by the amount of free memory you have. Due
to the complexity of this command it has been divided up into three
basic categories.
PART I - COMMAND LINE PARAMETERS
PART II - AUTOMATIC MESSAGE GENERATION
PART III - NODE ADDRESS SPECIFICATION
AREA Command
PART I - MAIN COMMAND LINE PARAMETERS
This section discusses the various command line parameters
available. Shown below is a sample command line.
AREA <drive:\directory> <area name> <area # or P>
Below is a description of these parameters.
<drive:\directory>
The physical DOS path specification for the specified
file area. This must be a valid drive and directory!
<area name>
This is the name of the file area you will be processing.
A maximum of 15 characters is allowed for the area name.
This name is similiar in function to the area definition
for a message conference in echomail.
<area # or P>
This is the file area number assigned in MAKEWILD. Range
is 1-999. If you want to make this area a PASSTHRU (a
method to which files are forwarded to other nodes, but
not added to your local database) then use the letter P
instead of a file area number.
WCFF! v3.51 Page 14
WCFF.CFG CONFIGURATION
AREA Command
PART II - AUTOMATIC MESSAGE GENERATION
Following the initial AREA command line paramters are statements
which can be used to make each file area unique. These OPTIONAL
commands will automatically override their POSTTOxxxx counterparts
in the main body of the WCFF.CFG file for the defined AREA only!
Shown below is a description of these commands.
LOCAL POSTTOAREA <local echo name>
This is used to create an echomail message that will contain
information about the file that was just added to your
database. You can use this feature to notify other users in
your network of new files. WCFF! creates a .PKT file in your
defined INMAIL directory and then you will need to run your
mail tosser to toss the message(s).
Example Usage: LOCAL POSTTOAREA Local_Sys
LOCAL POSTTOFROM <user name>
This option allows you to specify the FROM: field of the
echomail message that gets created if you use the LOCAL
POSTTOAREA option. Maximum of 36 characters.
Example: LOCAL POSTTOFROM Joe Martin
LOCAL POSTTOSUBJECT <text for subject line>
This option allows you to specify the content of the SUBJECT:
line of the echomail message that gets created if you use the
LOCAL POSTTOAREA option. Maximum of 72 characters.
Example: LOCAL POSTTOSUBJECT Look folks, new files!
LOCAL POSTTONOTE <note text>
This option allows you to specify the content of the note field
placed in the message body of the echomail message that gets
created. Maximum of 72 characters.
Example: LOCAL POSTTONOTE Files available for downloading
WCFF! v3.51 Page 15
WCFF.CFG CONFIGURATION
LOCAL POSTTOORIGIN <origin line>
This option allows you to specify the origin line you would
like appended to each echomail message that gets created.
Maximum of 66 characters allowed and it MUST include your
zone:net/node address enclosed in parenthesis.
Example: LOCAL POSTTOORIGIN The File Server BBS (1:161/504)
LOCAL CRC <ON|OFF>
This option is used to check the CRC-32 value in the .TIC file
against the actual CRC value of the file received. If there
is a match, this indicates the file is original (according to
the .TIC) and is then considered a valid/original file. If for
some reason the two CRC values do not match, the incoming TIC
file is then renamed to .BFF.
If this option is not used, then the CRC is not checked, but
all outgoing .TIC files created by WCFF! will have the correct
calculated CRC value in them.
Example Usage: LOCAL CRC ON or
LOCAL CRC OFF
AREA Command
PART III - NODE ADDRESS SPECIFICATION
The third and final section of the file AREA command is the
definition of the node addresses that files will be transferred to
and from.
Example Usage: <zone:net/node> <password> <flags>
Below is a description of these parameters.
<zone:net/node>
This is the full address of the node participating in sending
and receiving files.
<password>
Password associated with this file area to maintain security
for the defined node address. A maximum of 8 characters can
be used.
WCFF! v3.51 Page 16
WCFF.CFG CONFIGURATION
AREA Command - PART III (continued)
<flags>
The flag(s) after the password are used to define specific
operating characteristics for the node. Multiple flags can be
selected for each address, but must contain NO SPACES between
each flag. Below is a description of the available flags.
* Files from this address will be accepted. If this flag
is not present, files can be sent to the address, but no
files will be accepted from them.
& Files will not be sent to this address. If this is the
only flag for this address, then this address has
effectively been commented out, and no files will be
received or sent to this address. If you specify a "*"
with this flag then you will accept files from this
system, but no files will be sent to it.
C CRASH files will be generated for this address (a CLO in
Opus/Binkley mode)
H File is put in HOLD status for this address (a HLO in
Opus/Binkley mode)
F FLE files will be created for this address instead of
sending TIC files.
T Tells WCFF! to "not" send a .TIC file to this address.
An Tells WCFF! what AKA address to use. Where "n" is any
number "1" thru "9" and letter "A" thru "F". Please note
this is a HEX number where "A" is the 10th AKA and "F" is
the 15th AKA. Zero (0) is not allowed!
Sequential placement of AKA's (top to bottom) in the
WCFF.CFG file constitutes the numbering sequence used
with this flag. In other words, if the 3rd defined AKA
address was 86:250/0, then using the flag A3 would
indicate you wish to use 86:250/0 as the source address
of this file as indicated in the TIC/FLE file.
Example Usage: 86:250/100 password *CF
Again, please note there must be NO SPACES between flags if
more than one is used!
WCFF! v3.51 Page 17
WCFF.CFG CONFIGURATION
NEWFILESLIST <drive:\directory\filename> [OPTIONAL]
This option allows you to specify the full path and file name
to be created (or appended to) whenever WCFF! adds files to the
WILDCAT! database. This file can be used with automatic file
scanners (such as CATSCAN) for automatic virus scanning and so
on.
Example Usage: NEWFILESLIST c:\wc30\runlater.txt
WCFF! will check to see that the path specified does exist
prior to normal execution. The specified file generated by
WCFF! is a standard ASCII text file with a separate file name
on each line.
WCFF! v3.51 Page 18
ADDITIONAL INFORMATION
REVISION HISTORY
09/26/92 v3.51 Lowered memory requirements. Added new
command option NEWFILESLIST used for invoking
file scanning utilities. Cleaned up the full
screen hatch process. Various bugs fixed.
04/04/92 v3.50 Program has been renamed from WCFLFWD to
WCFF!. Complete rewrite including many major
enhancements. Refer to the section on New
Features for additional information.
08-01-91 v3.00 1st release of WCFLFWD v3.0 compatible with
WILDCAT! v3.00.
01-01-91 v1.02 Added CRC-32 checking on incoming TIC files.
A new WCFLFWD.CFG option of "CRC" will cause
WCFLFWD to check the incoming file for a valid
CRC-32. If it fails the CRC, the file is not
processed and the incoming .TIC file is
renamed to .BAD. All outbound TIC files will
have the correct CRC value in them, regardless
of whether you have CRC in the CFG file or
not. TABS are now ignored in the WCFLFWD.CFG
file.
09-15-90 v1.01 Added two command line switches. -N to not
delete .TIC's after WCFLFWD finishes. -T to
truncate files after they have been sent. The
-T is for Binkleyterm/Opus use only. The
v1.00 default was to truncate files, and this
version changes that. Please read the
documentation above.
06-15-90 v1.00 General release of WCFLFWD.
ERRORLEVELS
Upon program termination, either normally or abnormally, WCFF! will
register a DOS error level. This is usually not used except for
elaborate batch files that test for specific error levels upon
exit. If there are any errors encountered when exiting WCFF!,
these will be noted in the log file defined in WCFF.CFG and is
normally called WCFF.LOG.
Shown below is a list of possible DOS errorlevels WCFF! will return
upon exiting.
0 . . . Completed successfully
3 . . . Configuration file error
9 . . . Fatal Error
WCFF! v3.51 Page 19
TECHNICAL SUPPORT
TECHNICAL SUPPORT
You may contact Online Computer Resources at 1:161/503 via netmail
or by logging on to the BBS for technical support. We can also be
reached in the WILDCAT! conference on Fidonet. Business hours are
9am-6pm M-F and 10am-5pm Saturdays PST and our VOICE number is
(510) 687-1122.
When calling for support, be prepared to have a copy of your
WCFF.CFG file available. This MUST be the one you're CURRENTLY
using.
For even faster support, zip up your WCFF.CFG file, along with a
text file describing the problem, into a unique file name and send
them to our support board at:
(510) 687-0236 USR Dual Standard - 1:161/503
(510) 687-2134 V.32 9600 - 1:161/504
With your configuration file already on our system before you call,
we will be able to immediately look at your present setup and offer
any needed assistance much faster and more effectively. Please
help us help you.
WCFF! v3.51 Page 20
WCFF! LICENSING AND DISTRIBUTION AGREEMENT
COPYRIGHT (C) 1989, 1992 BY ONLINE COMPUTER RESOURCES. ALL RIGHTS
RESERVED. COMMERCIAL DISTRIBUTION AND/OR USE PROHIBITED WITHOUT
WRITTEN PERMISSION FROM ONLINE COMPUTER RESOURCES.
Non-Commercial distribution and/or use is permitted under the
following terms:
1) You may copy and distribute copies of WCFF! executable code
as you receive it, in any medium, provided that you do so in
a lawful, friendly manner and that you conspicuously and
appropriately publish on each copy of each file that is a part
of the distribution package a valid copyright notice:
"Copyright (C) 1989, 1992 by Online Computer Resources. Any
copies that you distribute must be distributed free of charge
to the recipient of the copy. WCFF! may not be sold and you
may not rent or lease it to any other person."
2) You must keep this License Agreement intact and give any other
recipients of the WCFF! program a copy of this License
Agreement along with the program.
3) You must distribute WCFF! in unmodified form. You may not add
an advertisement for your Bulletin Board System, User Group,
or anything else either as a file in the distribution packet
or as a header in any archive. You may not add, modify or
delete any of the files in the WCFF! distribution archive.
4) WCFF! must be distributed for free. You may not charge a
distribution fee for the physical act of transferring a copy
of this program. You may not place this program in any file
area of a Bulletin Board System where a fee is required for
download.
5) You may not modify your copy or copies of WCFF! or any portion
of it and you can not copy and distribute any modifications.
WCFF! is distributed in ZIP format and you may not distribute
it in any other form.
6) You may not copy, sublicense, distribute or transfer WCFF!
except as expressly provided under this License Agreement.
Any attempt otherwise to copy, sublicense, distribute or
transfer WCFF! is void and your rights to use the program
under this License agreement shall be automatically
terminated.
WCFF! v3.51 Page 21
WCFF! LICENSING AND DISTRIBUTION AGREEMENT
7) You may not incorporate parts of WCFF! into other programs
without the written permission of Online Computer Resources.
Permission may or may not be granted based upon a
determination of what your intended use is.
8) For the purposes of this document, "COMMERCIAL USE" is defined
as concurrent operation of the software on two or more
computers or data lines owned by the same for-profit
organization. Any organization may operate this software
under the terms of this Non-Commercial Agreement if operation
is limited to two or less computers or data lines.
9) You may use the software only after understanding and agreeing
upon the above terms.
NO WARRANTY
WCFF! v3.51 IS DISTRIBUTED AS AN EVALUATION COPY ONLY! THIS
PROGRAM REQUIRES THE USE OF A SPECIAL 30 DAY EVALUATION KEY
OBTAINABLE FROM THE WCFF! SUPPORT BBS AT (510) 687-0236. IF, AT
THE END OF THE 30 DAY PERIOD, YOU HAVE NOT REGISTERED THE PRODUCT,
WCFF! WILL SIMPLY CEASE TO RUN. REACTIVATION REQUIRES THE
PLACEMENT OF THE REGISTERED KEY FILE IN THE WCFF! DIRECTORY.
THIS PROGRAM IS GUARANTEED TO DO ABSOLUTELY NOTHING EXCEPT TAKE UP
DISK SPACE. USE IT AT YOUR OWN RISK. NEITHER ONLINE COMPUTER
RESOURCES NOR ANY OTHER PERSON INVOLVED IN IT'S DISTRIBUTION IS
RESPONSIBLE IN ANY WAY, FOR ANY DAMAGES RESULTING FROM ITS USE OR
MISUSE, DIRECTLY OR INDIRECTLY.
THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF WCFF! IS
ENTIRELY WITH YOU. SHOULD WCFF! PROVE DEFECTIVE, YOU ASSUME THE
COST OF ALL NECESSARY SERVICING, REPAIR OR OTHER DAMAGES TO YOUR
EQUIPMENT, SOFTWARE, OR OTHER PROPERTY.
ONLINE COMPUTER RESOURCES IS NOT RESPONSIBLE TO YOU FOR DAMAGES,
INCLUDING BUT NOT LIMITED TO, ANY LOST PROFITS, LOST MONIES, OR
OTHER SPECIAL, GENERAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE (INCLUDING BUT NOT LIMITED TO
LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED
BY THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY
OTHER PROGRAMS) OR ANY OTHER LOSS EVEN IF YOU HAVE BEEN ADVISED OF
THE POSSIBILITY OF SUCH DAMAGES, OR FOR ANY CLAIM BY ANY OTHER
PARTY.
WCFF! v3.51 Page 22
APPENDIX A
MEMORY REQUIREMENTS
Memory for WCFF! . . . . . . . . . . . . . . . . . . . . 250k
REQUIREMENTS/LIMITATIONS OF WCFF!
You can have different passwords for the same node for
different AREA's, and the password must be less than or equal
to 8 characters in length.
Area names are limited to 15 characters in length.
Try to keep all your directories that you specify in the
WCFF.CFG file to the same drive. WCFF! will rename the file
if it is on the same drive, and will copy and then delete the
file if on different drives. It is much faster to rename than
it is to copy and delete!
Points are not supported in this version. They may work, but
I haven't tested it.
Upper or lower case is not a problem. You can specify any
case!